Copyright: ModemTest 1.2


Overview
ModemTest by PassMark™ Software - Overview

ModemTest is an easy to use Windows based application that allows users to test their dial up modem. Two different test methods are provided. The first test method uses two telephone lines and two modems in a master / slave configuration. Based on user defined settings, the master can dial the phone number of the slave modem and after a successful connection, data packets are exchanged between the master and slave. Alternatively, standards based testing (eg. ITU-T v.56 ter) can be undertaken by specifying standards referenced test data files. The second test method requires only a single modem and no telephone line. A local loop back is done on the analog side of the modem, ModemTest then sends data packets which are echoed back by the modem.

In both cases ModemTest communicates to the modem using a COM port. (In the case of Internal modems or USB modems, this is a virtual COM port and not a physical plug on the machine). Before sending any data ModemTest first checks the settings on the serial port and then on the modem itself. Any data received is verified to be sure that it is complete and without errors.

A log of the activity is kept in the right hand section of the window. Different types of activity are highlighted in different colors. Any errors are displayed in red. This log can be saved to disk if required.

For more information click on one of the following topics.

How to start testing using a Master and a Slave

How to test ITU v.56 file transfer using a Master and a Slave

How to start testing using Diagnostic loop back

Understanding the display

The configuration window

The Activity log

Cyclic testing

Frequently asked questions

What’s new in this version

Copyright and license information

System requirements

Purchasing information

Contacting PassMark Software


How to start testing in Master / Slave mode
To start testing using a Master and a Slave

Steps to start testing

1.	You’ll need two modems, two telephone lines and preferably two PC’s. Make sure the modems are turned on and connected to their telephone lines and their respective PC’s.

2.	Start ModemTest on both PC’s. Select the mode “Master (Dialer)” on one and “Slave (Receiver)” on the other.

3.	On both PC’s, click on the “Config” button and check the correct COM port is selected. On the Master PC you also need to check that the correct phone number has been entered (this should be the phone number of the line that the slave modem is connected to).

4.	Select the test duration (in seconds).

5.	Set the Data transfer direction to Two-way.

6.	Set the Test data selection to Random Data.

7.	Click on the Start button on the slave. (the test must be started on the slave before the master)

8.	Click on the Start button on the master.

9.	If everything is setup correctly the master should dial the slave. The slave should automatically answer the call and then test data should be exchanged.


How to test ITU v.56 file transfer using method 1(Master / Slave)
To test ITU v.56 file transfer using a Master and a Slave

The Data transfer direction and the Test data selection options allow for testing against specific standards specifications, such as ITU-T v.56 ter, Test procedure for evaluation of 2-wire 4-kHz voiceband duplex modems.

Steps to testing

1.	You’ll need two modems, two telephone lines and preferably two PC’s. Make sure the modems are turned on and connected to their telephone lines and their respective PC’s.

2.	Start ModemTest on both PC’s. Select the mode “Master (Dialer)” on one and “Slave (Receiver)” on the other.

3.	On both PC’s, click on the “Config” button and check the correct COM port is selected. On the Master PC you also need to check that the correct phone number has been entered (this should be the phone number of the line that the slave modem is connected to).

4.	The Modem Init string should be set to configure the modem as required for each test. Refer to the ITU-T v.56 ter specification for the modem configuration required for each of the tests.

5.	Depending on the specific test being carried out, set the direction to either One-way or Two-way, as specified in the  ITU-T specification. A guide for this setting is included in the table following this list of steps. This is required on the Master and Slave PC’s.

6.	Set the Test data selection to Data file. This is required on the Master PC. This is required on the Slave PC if the file transfer is specified as Two-way.

7.	Specify the test file to be sent using the browse button marked “...” next to the File to send edit box. A guide for the send files is included in the table following this list of steps. This is required on the Master PC. This is required on the Slave PC if the file transfer is specified as Two-way.

8.	By directly typing into the File to receive edit box, specify the file name that you would like the received data to be stored in. Note that a directory path should not be specified, as the file will always be saved in the Receive directory . This is required on the Slave PC. This is required on the Master PC if the file transfer is specified as Two-way.

9.	Specify the number of times to send the test file within the same phone call , typically 1. This is required on the Master PC. This is required on the Slave PC if the file transfer is specified as Two-way.

10.	Specify the Delay between file transfers outlined in step 9. A guide for this setting is included in the table following this list of steps., typically 0 or 30ms. This is required on the Master PC. This is required on the Slave PC if the file transfer is specified as Two-way.

11.	Select OK. The configuration will be saved.

12.	Click on the Start button on the slave. (the test must be started on the slave before the master)

13.	Click on the Start button on the master.

14.	If everything is setup correctly the master should dial the slave. The slave should automatically answer the call and then test data should be exchanged.

Guide to ITU-T V.56 ter data transfer files (Based on version 08/96 of the ITU-T V.56 ter: Test procedure for evaluation of 2-wire 4-kHz voiceband duplex modems):

Test data file (specification reference)	Description of test
1X04.TST (6.1.2)	One-way transfer – send 1X04 test file from the Master to the Slave. This is used in test 6.1.2 of the ITU-T v.56 ter specification.
1X30.TST (6.2.5)	As above, for test file 1X30. Reference 6.2.5.
2X10.TST (6.1.1, 6.2.5)	As above, for test file 2X10. Reference 6.1.1 & 6.2.5.
3X06.TST (6.2.5)	As above, for test file 3X06. Reference 6.2.5.
4X04.TST (6.2.5)	As above, for test file 4X04. Reference 6.2.5.
5X16.TST (6.2.5)	As above, for test file 5X16. Reference 6.2.5.
FOX message - with delay (6.3.2)	As above, for set number of FOX messages with 30 milliseconds of delay. Reference 6.3.2.
FOX message – with no delay (6.4.5)	As above, for FOX message with no delay. Reference 6.4.5.
1X30.TST – two way transfer (6.2.6)	Two-way transfer – send 1X30 test file from the Master to the Slave and from the Slave to the Master. Both will commence on connection. This is used in test 6.2.6 of the ITU-T v.56 ter specification.
2X10.TST – two way transfer (6.2.6)	As above, for test file 2X10.TST. Reference 6.2.6.
3X06.TST – two way transfer (6.2.6)	As above, for test file 3X06.TST. Reference 6.2.6.
4X04.TST – two way transfer (6.2.6, Annex A)	As above, for test file 4X04.TST. Reference 6.2.6.
5X16.TST – two way transfer (6.2.6)	As above, for test file 5X16.TST. Reference 6.2.6.


How to start testing in local mode; Automatic testing; Command line
To start testing using Diagnostic loopback

Steps to start testing - Interactive

1.	Only a single computer and modem is required. Note that not all modems will support this loop back feature. Make sure the modem is turned on and connected to the PC’s.

2.	Start ModemTest on the PC. Select the mode “Local diagnostics”.

3.	Click on the “Config” button and check the correct COM port is selected.

4.	Click on the Start button.

5.	If everything is setup correctly ModemTest will configure the serial port and modem, retrieve the modem’s identity and then start sending out data packets. In this test mode only ten packets (about 3KB) will be sent out.

Steps to start testing – Automatic (from the command line)

To help automate the testing process, the diagnostic loopback test may be started from the command line.

1.	Only a single computer and modem is required. Note that not all modems will support this loop back feature. Make sure the modem is turned on and connected to the PC’s.

2.	Start ModemTest on the PC from the command line using:

ModemTest.exe  /l  <COM Port number> <Results file name>

For example, to start a local loop test (option /l), with a modem connected to COM port 1 and save the resulting data in the file “results.log” (in the same directory as ModemTest.exe), specify the following from the command line:

c:

cd "\program files\passmark\modemtest"

modemtest /l 1 results.log

3.	If everything is setup correctly ModemTest will configure the serial port and modem, retrieve the modem’s identity and then start sending out data packets. In this test mode only ten packets (about 3KB) will be sent out. The results will be saved in the specified file and ModemTest will close.


Display details
ModemTest Display

Mode: The mode determines which of the two available test methods will be used. The first test method uses two telephone lines and two modems in a master / slave configuration. The master dials the phone number of the slave modem and after a successful connection data packets are exchanged between the master and slave. The second test method requires only a single modem and no telephone line. A local loop back is done on the analog side of the modem, ModemTest then sends data packets which are echoed back by the modem.

Status: Indicates which test phase is currently being executed by ModemTest.

Packets sent: The number of packets transmitted. Each packet is 290 bytes in length and contains a time stamp, a packet sequence number, a 250byte random data payload and a 40bit checksum.

Packets rec.: The number of packets received.

Transmit speed: The transmission speed in Kilobytes per second, excluding start bits and stop bits. As the transmission standard used is 8 bits per bytes with no parity, 1 stop bit and 1 start bit, you need to multiply this Kilobytes per second figure by 10240 to get the raw number of bits transmitted per second. Eg. 3.20KB/Sec = 32768 bits / sec.

The figure of 10240 is 1024 (bytes per kilobyte) multiplied by 10 (bits per bytes).

Rec. Speed: The reception speed in Kilobytes per second.

Pkt Errors: The number of packets that arrived with an error. An error could mean that the complete packet did not arrive, there was a timeout waiting for a packet or that the checksum failed (i.e. the packet is corrupt). The percentage of packets in error is also displayed.

The activity log

In the right hand section of the window, there is an activity log with records the transactions that have taken place with the local or remote modem and any errors that have occurred. See the activity log section for more details.


Activity log description
Activity Log

The last 3000 transactions are logged in memory by ModemTest. If there are more that 3000 lines recorded in the log the oldest entry will be discarded. This log is displayed in the right hand portion of the ModemTest window. The log can also be saved to disk in text format using the “Save log” button.

The activity log records the following information.

COM Port Init: Transactions to configure the COM port on the PC. These transactions are highlighted with a green background.

Modem Port Init: Transactions to configure the modem connected to the COM port. One particular line of interest is the one that contains the CONNECT statement. This shows the speed that the modems have negotiated. These transactions are highlighted with a blue background.

Sent data: A record is kept of data that was transmitted. Each time 100 packets have been transmitted a new entry is made in the log. The entry includes the time in seconds since data transmission started, the number of packets transmitted and the number of bits transmitted These transactions are highlighted with a light blue background.

Received data: A record is kept of data that was received. Each time 100 packets have been transmitted a new entry is made in the log. The entry includes the time in seconds since data transmission started, the number of packets transmitted, the number of bits transmitted and the current error count. These transactions are highlighted with a pink background.

Errors: Any errors that occurred are logged. In the case of an error in a data packet the packet number is included. These transactions are highlighted with a red background.

Other information (displayed with a white background): Includes:

•	Opening, re-opening and closing of the test file to be sent;

•	Opening and closing the test file to be received.


Configuration
Configuration window

There are several settings that can be changed from the configuration window.

COM Port

A list of the 1st dozen COM ports are displayed. Those that are marked as ‘In Use’ are already being used by another device (e.g. your mouse). Those COM ports that are marked as ‘unavailable’ could not be detected as being installed in your computer. Those that are marked as ‘available’ have the potential to have a modem attached.

Port speed

A modem has two interfaces. One for your computer and one for the telephone network. The port speed is the speed at which your modem and PC communicate. All new computers and modems should work at 115,200bps.

Test duration

This affects how long the Master / Slave test will take to complete.

Note: When a test is run in Two-way mode with random test data, the duration of the test will be the minimum of the settings on the Master and Slave sides. It is suggested that the Test duration value be set to equal values on both the Master and Slave side.

Connection timeout

This is the amount of time the software will wait to get a connection after dialing the remote number. 30 sec is usually a good amount of time.

Phone number

This is the phone number that is used by the slave machine. For most modems the following additional codes can be used.

The letter T can be included to force the modem to tone dial (rather than the old style pulse dialing). Most modems default to tone dialing in any case., e.g. T543123456

The letter W can be included to wait for a second dial tone. e.g. 0W543123456

A comma ‘,’ can be used to include a pause in tone dialing. e.g. 1,,54,3123456

Space characters, hyphens and parentheses are ignored by most modems.

Modem Init string

This field allows the user to enter their own modem initialization string. This is sent to the modem before the start of the tests. Typical examples would be.

ATV1 = Force the modem to return word results instead of numeric response codes. (ModemTest expects word results, which are the default on most modems).

ATL0 = Sets the modem speaker to a low level

ATL3 = Sets the modem speaker to a high level

Repeat test cycles indefinitely (Delay and clearing results)

See the section on Cyclic testing for details

Transmission timeouts

This setting affects how long ModemTest will wait for data to be transmitted or arrive. Longer times should be used with slower connection speeds because data will be slower to arrive or depart.

Data Transfer Direction

Two-way: This setting results in the Master and Slave sending data simultaneously. This is the default.

One-way: This setting results in only the Master sending data. The Slave will only receive data.

Test Data Selection

Random data: This setting results in the Modem test program generating random data for the test. This is the default.

Data file: Where the sending and receiving of specific test files are required, this option can be selected. When this is selected, the following additional information is required:

•	File to send: This allows the selection of the test file to be sent (directory and filename). This information can be either be (i) typed in directly or  (ii) the “...” button selected to allow browsing to the required file.

•	File to receive: This allows the filename where the received data will be stored to be entered. This file will always be stored in the <ModemTest directory>\receive\ directory (eg. C:\Program Files\Modem Test\Receive\).

•	Run test file transfer: This setting allows for a data file to be sent a specified number of times within the same connection (phone call).

•	Delay between cycles: When a test file transfer is repeated using the above selection, a delay (in milliseconds) can be added between the sending of files within the same connection.


Cyclic testing

By changing the options on the configuration screen, ModemTest can be configured so that the tests repeat them selves in a cyclic manner. This can be a useful option for stress testing modem or telephone exchange equipment. There are three options that can be set.

Repeat test cycle indefinitely

Setting this option will result in the selected test being repeated in a never ending cycle. The cycle can be stopped by pressing the stop button while between two tests.

Delay between cycle

The amount of time in seconds between test cycles.

Clear results between cycles

Setting this check box will prevent the statistics and log file from being cleared at the start of each test cycle.


Contacting PassMark
Contacting PassMark™ Software

On the Web

You can contact PassMark on the web at

http://www.passmark.com

E-Mail

For technical support questions, suggestions

help@passmark.com

For sales & commercial issues

sales@passmark.com

For any other issues

info@passmark.com

FAQ

You may also want to check out the list of Frequently Asked Questions .


Ordering and License
Purchasing information

Price

US Dollars:	$15  (Single user)

 from the PassMark Software web site

See the PassMark website  http://www.passmark.com/sales for details of multiuser pricing and site licenses

What happens when you order

After the order is accepted by our sales agent, a license Key will be returned (via E-Mail, Fax or normal mail). This Key is then entered with the User Name into the initial, ‘Welcome’ window. At this point the program then changes permanently into the licensed version. Keys are normally returned within 12 hours or less.

What you get when you purchase the software

•	Free Technical support via the Web and E-Mail

http://www.passmark.com/support

•	Free minor upgrades & bug fixes as they become available

http://www.passmark.com/download

•	The removal of the initial shareware startup window

•	The removal of the 30day evaluation period associated with the shareware version.

How to order

Online

If you would like to purchase ModemTest, you can do so online using a credit card via a secure connection at

http://www.passmark.com/sales

Offline

You can also order over the phone, via a PurchaseOrder or Fax, see our web page for details

http://www.passmark.com/sales

Other information

Confidentiality

All personal details supplied when placing an order will be strictly confidential. Online orders will only be accepted over a secure, encrypted connection.

Multi-user & Site Licenses

Contact PassMark software, asking about our attractive rates for Multi-user and site licenses.

http://www.passmark.com/sales

sales@passmark.com

User Names and License Keys

Both the User Name and License Key must be correctly entered before the software turns itself into the licensed version. Be careful because the Key is case sensitive (upper case characters must be entered in upper case and lower case characters must be entered in lower case). The User Name and Key should be kept in a safe place in case the software ever needs to be reinstalled. Step by step instructions are available online, if required,

http://www.passmark.com/support/keyhelp.htm

Questions & more information

If you have any questions we would be happy to hear about them. Contact

sales@passmark.com


System Requirements

80486 50Mhz or faster.

Windows 95, Windows 98, WinMe, WindowsNT, Window 2000, XP

(Windows95 and NT4 require Internet Explorer 4 or above to be installed)

32Meg RAM

1 Meg of free hard disk space to install the software

A compatible dial up modem. (56K or slower)

The modem must support the traditional Hayes AT command set. The modem must also support the analog loopback function if the stand-alone test feature is used. (Almost all modems support the AT command set. Most newer modems also support the loopback feature)

ISDN, ADSL and cable modems are not supported.


Copyright and License
Copyright & License information

Copyright & End User license

This End-User License Agreement (“EULA”) is for the PassMark™ ModemTest software.

EULA is a legal agreement between you (either an individual or a single entity) and PassMark Corporation for the PassMark software product identified above, which includes computer software and may include associated media, printed materials, and “online” or electronic documentation (“SOFTWARE PRODUCT”).  By installing, copying, or otherwise using the SOFTWARE PRODUCT, you agree to be bound by the terms of this EULA.  If you do not agree to the terms of this EULA, do not install or use the SOFTWARE PRODUCT.

1. GRANT OF LICENSE. This EULA grants you the following rights:

•	A license is granted only after the payment of the license fee.

•	If no license fee has been paid the product can be used for evaluation purposes for a maximum period of 30 days.

•	After the license fee has been paid, you may install and use one copy of the SOFTWARE PRODUCT, or any prior version on a single computer, or on a single removable disk. The SOFTWARE PRODUCT must NOT be installed on a network where it could be used by more than a single computer unless a multiuser license has been purchased..

•	The primary user of the computer on which the licensed SOFTWARE PRODUCT is installed may make a second copy for his or her exclusive use on a portable computer.

0	2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

•	Limitations on Reverse Engineering, Decompilation, and Disassembly.

You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT.

•	The shareware version of the software may be freely distributed provided that no fee is charged and the product is distributed complete and intact.

3. COPYRIGHT.

All title and copyrights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and “applets” incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by PassMark. The SOFTWARE PRODUCT is protected by copyright laws and international treaty provisions. Therefore, you must treat the SOFTWARE PRODUCT like any other copyrighted material except that you may install the licensed SOFTWARE PRODUCT on a single computer provided you keep the original solely for backup or archival purposes.

LIMITED WARRANTY.

PassMark warrants that (a) the licensed SOFTWARE PRODUCT will perform substantially in accordance with the accompanying written materials for a period of ninety (90) days from the date of receipt, and (b) any Support Services provided by PassMark shall be substantially as described in applicable written materials provided to you by PassMark, and PassMark support engineers will make commercially reasonable efforts to solve any problem issues. Some states and jurisdictions do not allow limitations on duration of an implied warranty, so the above limitation may not apply to you. To the extent allowed by applicable law, implied warranties on the SOFTWARE PRODUCT, if any, are limited to ninety (90) days.

No warranty of any sort of offered on the evaluation version of the software, until a license fee is paid.

Additional information

For questions regarding the copyright, end user license contact, multi-user licenses and site licenses, contact.

info@passmark.com


Problems and FAQ
Problems and Frequently Asked Questions (FAQ)

Note: See the PassMark website (www.passmark.com) for the latest version of the FAQ

Q. How do I know which serial port (COM port) to select in the configuration window.

In the configuration window a list of COM ports is displayed. Those that are marked as In Use are already being used by another device (e.g. your mouse). Those COM ports that are marked as unavailable could not be detected as being installed in your computer. Those that are marked as available have the potential to have a modem attached. So if you are not sure which one to select try each Available port in turn. External modems tend to use serial ports 1 or 2. Internal or USB modems tend to use ports 3 or 4. There is no fixed rule however.

Q. What Port speed should I use.

A modem has two interfaces. One for your computer and one for the telephone network. The port speed is the speed at which your modem and PC communicate. The connection speed, also known as line speed, is the speed at which the modem connects to another modem across the telephone network. Both speeds are measured in bits per second (bps). Most serial ports can reach at least speeds of 115,200bps. This is much faster than the connection to the telephone network, which is typically 33,000bps or 56,000bps. If the modem is using compression then the effective bit rate can be higher than this. To avoid problems of slow transmission you should always select a port speed that is higher than the connection speed. Most PC don’t support port speeds of 128,000 or above, so 115,200 bps is usually a good choice. If you try and select a speed which is not available you will get an error like, “Unable to configure the serial port, The parameter is incorrect”

Q. I get the error, “Unable to detect modem on this COM port” What’s wrong.

Check the following.

1. The modem is turned on

2. The modem is connected to the computer

3. The correct serial (COM) port is selected. (see above)

4. The modem is not already in use by another application (e.g. your internet connection, fax software)

Q. I have a problem getting a connection, maintaining a connection or the connection is slow.

Check the following.

1. Call waiting is turned off. Call waiting tones can interfere with modem communications.

2. Try to disconnect all other telephone devices (telephone handsets, answering machines, faxes, cordless phones, etc..) connected to the same phone line as the modem.

3. Temporally remove extra devices such as surge suppressors, splitters, phone line extenders, etc… Plug the modem directly into the wall.

4. Check that the telephone cable is plugged into the LINE socket on the modem and not the PHONE socket. Note that not all modems will have both sockets in any case.

5. Check that no one else is using a phone that is connected to the same line as the modem.

6. Check that the correct slave phone number is entered for the computer configured as the Master.

7. Check that the slave has been started and is waiting to receive a call.

8. For modems that have firmware that can be reprogrammed, check with the modems manufacturer that you have the latest version.

9. Check that the modem you are trying to connect to supports the same standards. (There were until recently several different standards for 56Kbps modems, these were called, x2 and K56flex. These have now both been superceded by V.90)

Q. My connection speed varies from one call to the next, why.

The connection speed of a modem is limited by the telephone network. The telephone network was designed to carry the human voice and because of this, there is fairly low limit on how much data can be pushed through the network. Modems that use the V.34 standard (28.8Kbps & 33.6Kbps) as well as the newer V.90 standard (56Kbps) are at the limits of what the telephone network can handle. In general it is only under ideal conditions on a high quality telephone network that the maximum transmission speeds can be obtained.

When the slave modem answers there is a brief period of negotiation to determine the maximum speed that can be supported. The same modem may perform quite differently when used from a different location or when it is used to call a different destination. Also, as this negotiation period is fairly brief the speed negotiated can vary significantly from one call to the next due to small differences in line quality.

Q. I have a 56Kbps modem but ModemTest never connects at this speed.

To use 56Kbps there must be only one analog to digital conversion between your modem and the destination. You have no control over this as it is dependant on your telephone company’s infrastructure. In order to connect at 56Kbps the destination modem must be connected with a digital line, this might be a T1 line (E1 in Europe). Thus with ModemTest, which uses two analog modems, with two analog phone lines 56Kbps will never be possible. 33.6kbps will be the normal maximum. However if your 56Kbps modem successfully runs at 33.6Kbps with ModemTest, then higher speeds will be possible with ISPs who have a direct digital connection. This is shown in the diagrams below (for data transmitted from the left computer to the right computer).

There is however some other issues to be aware of. There were until recently several different standards for 56Kbps modems, these were called, x2 and K56flex, these have now both be superceded by V.90 and they don’t all work together.

Also, even with a 56Kbps modem in perfect conditions the connection is asymmetric. You can only get 56Kbps in one direction (downloads). For uploads you are limited to 33.6Kbps. By contrast, with lower connection speeds you get the same speed in both directions. Some PABX’s (company switchboards) will also stop 56Kbps connections from being established.

Q. In local diagnostic mode, the transmit and receive speeds are lower than they should be.

In this local diagnostic mode a data packet is sent to the modem, then ModemTest pauses waiting for the modem to echo the packet back to the PC. Because of this pause in transmission the full data rate will never be achieved with the local test. This is not the case for the master / slave test method where multiple software threads are used to transmit and receive data as fast as the modem and PC will allow.

Q. Can ISDN, ADSL or Cable modems be tested with ModemTest.

No. Only dial up modems are supported. In most cases it is not possible to directly connect ADSL and Cable modems directly to each other. ISDN may be a possibility for future versions of the software.

Q. I am using Windows ME. When running local diagnostics, I get error like, " Missing data: 288 bytes expected. 116 bytes received". or "ERROR, Packet is X% corrupt. Offset: X. Bytes Out: XXX, Bytes In: XXX", Why ?

We have seen this problem with a few different internal PCI modems (soft modems) from various different manufacturers. Investigation are still ongoing, but now point to this being a bug in the Microsoft Windows WDM driver when using the VCOMM interface in Windows ME. This problem should not affect your modem when connecting to your ISP however. The Microsoft driver seems to ignore time-out settings. This problem only affects Windows ME. Setting very long timeout period may help work around this problem.

Q. I am using Windows95 or NT4 and ModemTest doesn’t run. I see an error about a missing file.

If you are running Windows95 or Windows NT4 you need to have Internet Explorer version 4 or above installed. There are some Windows operating system updates that are installed with Internet explorer that are required for ModemTest. This is not required in later version of Windows.

Q. In Master / Slave mode the master hangs up before a connection can be established with the slave.

It might be because the Master timed out waiting for a connection. Try increasing the timeout value in the configuration window.

Q. I get an error like, “Unable to detect modem on this COM port: No additional info”, “Invalid modem response: 0”

The modem may be returning numeric response codes instead of word result codes. Use ‘ATV1’ in the modem init string for force word results.


Whats new - version history
What new - Version history

V1.3.1004, 18/Jun/2003

Minor Enhancement

To help automate the testing process, the diagnostic loopback test may now be started from the command line.

V1.3.1000, 24/Dec/2002

Major Enhancement

Allows for the testing of the transfer of specific data files such as against specific standards specifications, eg. ITU-T v.56 ter, Test procedure for evaluation of 2-wire 4-kHz voiceband duplex modems.

•	Introduced the capability to send a specified data file, to repeat the transfer of the information in the test file (within the same connection) and to introduce a delay between the the sending of these files.

•	Introduced One-way data transfer.

V1.2.1004, 12/Aug/2002

Minor Bug fix

•	Allowed transmission timeouts to be adjusted by the user. Longer timeouts correct problems with modems that use low baud rates for the loopback test.

•	Added an extra step in the Modem initialization process to restore factory settings. (Master / Slave mode)

V1.2.1000, 10/June/2002

Major Bug fix

•	Correction of a serious bug that caused random packet errors with some modems (particularly soft modems).

•	Work around for Windows bug causing thread locking when checking receive buffer size

V1.1.1005  8/May/2002

Minor Enhancement

•	Added field for user defined modem init string.

V1.1.1004  31/Mar/2002

Minor Enhancement

•	Added options to allow cyclic testing to be performed.

•	Added connection timeout field

V1.1.1002  12/Feb/2002

Minor bug fixes

•	Bug fix to stop modems that return long diagnostic strings  being flagged as an incorrect.

•	Additional logging of program version and windows version.

V1.1.1000  31/Oct/2001

Minor release for Windows XP

•	New release to better support the Windows XP user interface.

•	Addition of date and time stamp to saved log file

•	Extra log file information for a failed local loop back test.

V1.0.1001  15/Oct/2001

•	Bug fix that corrects log control position for displays running at greater than the standard 96dots per inch.

V1.0  1/Oct/2001

First release.

•	First full release